The latest updates on your projects. Learn more about Vercel for GitHub.

1 Skipped Deployment

Project	Deployment	Review	Updated (UTC)
docs	Skipped		Jan 21, 2026 10:41am

Greptile Summary

Fixed the secureFetchWithPinnedIP function's custom DNS lookup implementation to properly handle Node.js agent options parsing. The lookup function now correctly handles the options.all parameter by returning an array of address objects when all: true, or individual values when all: false. Additionally, the accept-encoding header is now removed before making requests since Node.js http/https modules don't automatically decompress responses.

Key Changes:

• Imported LookupFunction type from 'net' module for proper type safety
• Fixed lookup function to handle both options.all cases correctly
• Added explicit type annotation http.AgentOptions for agent configuration
• Removed accept-encoding header from requests to prevent compression issues
• Improved code structure by extracting lookup function outside agentOptions

Confidence Score: 5/5

• This PR is safe to merge with minimal risk
• The changes fix a legitimate bug in the DNS lookup function where options.all wasn't being handled correctly, which could cause runtime errors when the http/https agent internally calls the lookup function. The fix properly implements the LookupFunction interface from Node.js, adds appropriate type safety, and removes the accept-encoding header which prevents potential decompression issues. The changes are localized, well-commented, and improve code correctness without introducing new risks.
• No files require special attention

Important Files Changed

Sequence Diagram

sequenceDiagram
    participant Client as Tool Executor
    participant Validator as validateUrlWithDNS
    participant DNS as DNS Resolver
    participant Fetch as secureFetchWithPinnedIP
    participant Agent as HTTP/HTTPS Agent
    participant Server as External Server

    Client->>Validator: validateUrlWithDNS(url)
    Validator->>DNS: dns.lookup(hostname)
    DNS-->>Validator: resolvedIP
    Validator->>Validator: Check if IP is private/reserved
    Validator-->>Client: {isValid, resolvedIP}
    
    Client->>Fetch: secureFetchWithPinnedIP(url, resolvedIP, options)
    Fetch->>Fetch: Create lookup function with pinned IP
    Note over Fetch: lookup handles options.all case:<br/>returns [{address, family}] or (address, family)
    Fetch->>Fetch: Remove accept-encoding header
    Fetch->>Agent: Create Agent with custom lookup
    Fetch->>Server: HTTP/HTTPS request with pinned IP
    Note over Agent,Server: Agent uses lookup function<br/>to force connection to resolvedIP
    Server-->>Fetch: Response
    Fetch-->>Client: SecureFetchResponse

@cursor review